Be sure not to clobber existing files when installing dotnet.#1788
Merged
JamesWTruher merged 1 commit intoPowerShell:masterfrom May 23, 2022
Merged
Be sure not to clobber existing files when installing dotnet.#1788JamesWTruher merged 1 commit intoPowerShell:masterfrom
JamesWTruher merged 1 commit intoPowerShell:masterfrom
Conversation
This is the same fix as PowerShell/PowerShell#17141
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is the same fix as PowerShell/PowerShell#17141
PR Summary
installing a new dotnet will clobber the current executables causing all sorts of trouble (dotnet will stop working entirely)
PR Checklist
.cs,.ps1and.psm1files have the correct copyright headerWIP:to the beginning of the title and remove the prefix when the PR is ready.